-
Notifications
You must be signed in to change notification settings - Fork 8
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Update DFG::combineForIter() #21
Conversation
I didn't get the fusion about 0, 11, 20 DFG nodes. Can we have a sync on this? |
Can this currently be used as a parameter/argument set inside the |
And what about unrolling factor = 3? |
And can you also provide a fused DFG that both the unrolling and the |
I didn't see my previous comments are addressed? |
No. Below is an example using it (in DFG.cpp).
|
For the And do you know why the edge from |
If we want to keep the blue edge, we should guarantee that the nodes of the blue edge are PatternRoot. Otherwise, the blue edge will be replaced by a red edge. See https://github.com/tancheng/CGRA-Mapper/blob/master/src/DFG.cpp#L76 To keep the blue edge, we may need to modify the replaceDFGEdge(). |
ha, so for now, one ctrl edge out of the two edges will become data edge. Then do you think you can fix this in this PR? |
I hope I can fix it this week in this PR.
…------------------ Original ------------------
From: Cheng Tan ***@***.***>
Date: Tue,Jun 11,2024 6:10 PM
To: tancheng/CGRA-Mapper ***@***.***>
Cc: MeowMJ ***@***.***>, Author ***@***.***>
Subject: Re: [tancheng/CGRA-Mapper] Update DFG::combineForIter() (PR #21)
ha, so for now, one ctrl edge out of the two edges will become data edge. Then do you think you can fix this in this PR?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: ***@***.***>
|
Thanks! |
…l edge on the newly added edge
I find two bugs in combineForIter() when I am debugging combineForUnroll() (because they share key codes).